Reliable Data Transmission with Reduced Bit Error Rate

ABSTRACT

A data transmission system includes at least one transmission line. A sender is configured to send data frames to the at least one transmission line and a recipient is configured to receive the data frames from the at least one transmission line. The sender and the recipient are both configured to determine a check sum based on a plurality of corresponding data frames that are sent to and, respectively, received from the at least one transmission line. A check sum comparing unit is configured to receive and to compare the check sum determined by the sender and the corresponding check sum determined by the recipient. The check sum comparing unit is also configured to signal a transmission error or initiate a safety function when the check sums compared are not equal.

TECHNICAL FIELD

The present invention relates to the field of digital data transmission and, in particular embodiments, to reliable transmission of digital data frames to reduce bit errors in received data frames.

BACKGROUND

There are many known ways for detecting whether a sequence of a certain number of bits (also called “data frame” or simply “frame”) includes erroneous bits due to errors during transmission or storage of a data frame. One common way is to include further data bits in the data frame which represent a check sum (also called hash sum). For example, a single parity bit may represent a very simple check sum. However, more sophisticated procedures (so called hash functions) for calculating check sums are known. Another common example for a hash function which may be used for generating check sums is called “cyclic redundancy check” (CRC) or “polynomial code checksum.” Dependent on the order of the polynomial which is in such a procedure, it is referred to as CRC4, CRC12, CRC64, etc. (i.e., a CRC using a polynomial of order 4, 12, 64, etc.). For example data transmissions via an Ethernet network or transmissions from and to a hard drive are checked by CRC methods.

Different CRC procedures using polynomials of different lengths (generally different check sum methods) are typically associated with a certain probability that a received bit is incorrect but not detected. One application in which bit errors may have fatal consequences are electronic control units (ECUs) that control the deployment of the airbags installed in an automobile. In such applications the probability of an undetected bit error (bit error probability) and the bit error rate are closely related to the probability of an accidental deployment of an airbag which may have fatal consequences. For this reason the relevant standards such as ISO 26262 (titled “Road vehicles—Functional safety”) define so-called “safety integrity levels” (e.g., ASIL A to ASIL D, whereby ASIL is short for “automotive safety integrity level”) which are associated with different upper limits for the probability of failures dependent on the risk related to such failure.

In view of the extremely high requirements for the detection of errors in transmitted data frames, particularly in automotive applications, there is a need for improved methods and systems allowing for a reliable data transmission.

SUMMARY OF THE INVENTION

A data transmission system is disclosed. In accordance with one example of the invention the system comprises at least one transmission line, a sender that is configured to send data frames to the at least one transmission line, and a recipient that is configured to receive the data frames from the at least one transmission line. The sender and the recipient are both configured to determine a check sum based on a plurality of corresponding data frames which are sent to and, respectively, received from the at least one transmission line. The data transmission system further comprises a check sum comparing unit that is configured to receive and to compare the check sum determined by the sender and the corresponding check sum determined by the recipient, the check sum comparing unit being further configured to signal a transmission error or initiate a safety function when the check sums compared are not equal.

Further, a bus system is disclosed. In accordance with another example of the invention such system comprises at least one bus line, a sender that is configured to send data frames to the at least one bus line, and a recipient that is configured to receive the data frames from the at least one bus line. The sender and the recipient are both configured to determine a check sum based on a plurality of corresponding data frames which are sent to and, respectively, received from the at least one bus line. The data bus system further comprises a check sum comparing unit that is configured to receive and to compare the check sum determined by the sender and the corresponding check sum determined by the recipient, the check sum comparing unit being further configured to signal a transmission error or to initiate a safety function when the check sums compared are not equal.

Additionally, a method for transmitting data frames from a sender to a recipient over a transmission channel is disclosed. In accordance with a further example of the invention the method comprises determining, on the sender's end, a check sum based on a plurality of data frames which are sent. On the recipient's end, a check sum based on a plurality of corresponding data frames which have been received is determined. The check sum determined by the sender and the corresponding check sum determined by the recipient are compared, and a transmission error is signaled when the check sums compared are not equal.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention can be better understood with reference to the following drawings and description. The components in the figures are not necessarily to scale, instead emphasis being placed upon illustrating the principles of the invention. Moreover, in the figures, like reference numerals designate corresponding parts. In the drawings:

FIG. 1 is a block diagram illustrating the basic components of an ECU that controls the airbag deployment in an automobile;

FIG. 2 is a block diagram illustrating one example of bus interfaces connecting an ECU to external sensors and operating in accordance with a first example of the invention;

FIG. 3 is a block diagram illustrating another example of bus interfaces connecting an ECU to external sensors and operating in accordance with a second example of the invention; and

FIG. 4 is a block diagram illustrating a further example of bus interfaces which operate in accordance with a third example of the invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The making and using of the presently preferred embodiments are discussed in detail below. It should be appreciated, however, that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention. In the further description the invention is described using an airbag ECU (electronic control unit) as an example, whereby the ECU communicates with external sensors via an SPI (short for “serial peripheral interface”) bus system. However, other applications of the inventive concept exist.

FIG. 1 is a block diagram illustrating the basic components of an ECU 10 (electronic control unit) that controls the airbag deployment in an automobile. The airbags are deployed (“fired”) using so-called squibs. A squib 40 is fired by supplying it with a respective electrical current. A squib usually has two terminals, one being coupled to a low side supply potential V_(SS) via a low side transistor T_(LS) and one being coupled to a high side supply potential V_(CC) (or V_(DD)) via a high side transistor T_(HS). If both transistors are driven into an on-state (conducting state of low resistivity) the whole supply voltage V_(CC)-V_(SS) is applied to the squib 40. In order to prevent an accidental firing of the squib 40 a blocking transistor T_(B) is further coupled in series to the squib 40 and the transistors T_(HS), T_(LS) such that a firing of the squib is prevented if the blocking transistor is driven into an off-state (non-conducting state of high resistivity). The blocking transistor T_(B) is driven into its off-state when inconsistency is detected in received data which is relevant for the deployment of an airbag. The transistors T_(HS) and T_(LS) are driven by a firing logic unit 131 whereby in the present example the transistors T_(HS) and T_(LS) are implemented as MOSFETs and thus the firing logic unit 131 includes appropriate gate drivers for generating the gate signals in accordance with an input signal supplied to the firing logic unit 131. The transistors T_(HS) and T_(LS) and the firing logic unit 131 compose, inter alia, an airbag deployment interface 13. Further, the blocking transistor T_(B), a respective driver 142, and a corresponding safety integrity check unit 141 compose, inter alia, a safety circuit 4 which is adapted to prevent unwanted deployment of an airbag due to inconsistent or corrupt data which is relevant for airbag deployment.

The mentioned input signal to the airbag firing interface 13 is provided by a microcontroller unit 12 (MCU) which receives data from external sensors 20 via a bus interface unit 11. The bus interface unit 11 communicates with the external sensors 20 via bus lines 30. In the present example the bus interface unit 11 includes, e.g., a PSI5 (short for: Peripheral Sensor Interface 5) interface managing the communication with the external sensors 20 and an SPI interface which is used for communicating the information received from the external sensors 20 to the internal SPI bus of the ECU 10. Thus, the bus interface unit 11 may be seen as bridge unit that allows the sensors 20 to communicate with the MCU 12 via a standard interface such as SPI. The external sensors may employ a different standard to communicate with the bus interface unit 11, such as PSI5 (as illustrated in the example of FIG. 1), DSI (short for: Digital Signal Interface), LIN (short for local Interconnect Network), CAN-bus or the like. Different standards may be used for connecting different types of external sensors 20 to one ECU 10. The above mentioned safety circuit 4 (or parts thereof) may be implemented in the MCU 12 using appropriate software. However, it might be preferable to provide separate and independently operable hardware for the safety circuit 4. For this purpose the safety circuit may be implemented on a separate silicon die.

The external sensors 20 may be provide information relevant for airbag deployment. Such information may cover, inter alia, seat occupancy, acceleration, atmospheric pressure inside the doors, driving direction, velocity, etc. As mentioned, the respective sensors 20 may communicate with the bus interface unit 11 of the ECU 10 via a two-wire sensor interface such as, for example, the Peripheral Sensor Interface 5 (PSI5) which is common in automotive applications for connecting sensors to other electronic circuits such as, for example ECU 10. However, any other communication standard suitable for connecting the external sensors 20 to the ECU 10 may be applicable.

As mentioned above, the SPI interface 11 of the ECU 10 receives data, which may be relevant for airbag deployment, from external sensors 20 (also called “satellite sensors”) and forwards the information to the MCU 12 (and, when necessary, also to the safety circuit 4 via the MCU 12) using a standard bus system such as the SPI which is included in many commonly used microcontrollers. In some applications it is desirable to deploy the airbags (e.g., the side airbags) based on information provided solely by the mentioned external sensors 20. In such cases all the data relevant for airbag deployment has to pass the bus lines (e.g., the SPI bus lines) connecting the SPI interface 11 and the MCU 12 of the airbag ECU 10. In such cases the bus communication has to comply with high safety requirements and a sufficient safety margin has to be assured even under worst case conditions such as, for example, environmental conditions leading to maximum signal distortion, wire break, broken solder joints on the circuit board, etc., all of these examples leading to a significantly increased bit error probability. In the present example of an airbag ECU the whole electronic system controlling the airbag deployment has to comply with the requirements of ASIL D (according to ISO 26262) which demands a failure in time (FIT) rate of less than 10⁻⁸ per hour. The bit error rate of data transmissions over the SPI bus has to include an additional safety margin as it is not the only component which contributes to the overall system failure rate and should thus achieve a FIT rate of less than 10⁻¹⁰ per hour. However, the actual numerical value may be different in different applications.

Assuming the mentioned FIT rate of 10⁻¹⁰ per hour a corresponding bit error probability may be calculated dependent on the method which is used for providing check sums so as to be able to detect corrupt data frames received from the SPI bus. For example, when using a CRC method with a polynomial of 4^(th) order and a Hamming distance of two, the corresponding tolerable bit error probability is 3·10⁻¹⁰. When using a CRC method with a polynomial of 8^(th) order and a Hamming distance of four, the corresponding tolerable bit error probability is about 1.5·10⁻⁵. These calculations are based on a typical system including two external sensors which deliver data samples each 500 microseconds whereby transmission errors should be detected in 32 bit data frames. The calculation of extremely low bit error probabilities cannot be assured in a real environment. Thus, some improvements of the check sum calculation method are suggested so as to allow for higher bit error probabilities without increasing the respective FIT rate required by ASIL D.

Simply increasing the order (e.g., CRC16 or CRC32) of the polynomial used in the CRC method can contribute to improve the situation. However, a high order CRC would entail an increased data volume transmitted over the bus lines and thus would require a higher bus clock rate which may be undesired in some applications and may have a negative influence on the bit error probability. A transmission over redundant hardware channels would increase the hardware complexity which may also be undesired. Alternatively, a second CRC using a high order polynomial (e.g., CRC 32 or CRC 64) may be applied to a group of subsequent data frames (e.g., a group of 20 frames of 32 bits) whereby each single data frame is protected by a low order CRC (e.g., CRC4 or CRC8). Such second CRC significantly alleviates the requirements to the bit error probability.

The additional CRC check sum is not transmitted over the bus lines together with every data frame. The check sum is rather updated each time a new data frame is transmitted and this check sum will depend on (and thus represent) all data frames transmitted after a reset of the check sum. The current value of the check sum may be requested by a designated bus command (an SPI command in the present example). The bus master may request the “cumulative” CRC check sum at least once after a defined number of frames have been received from the bus slave. Further the cumulative check sum may be requested if the sensor data received from the bus includes information that would lead to a deployment of the airbag(s).

The additional check sum mentioned above is calculated on the sender's end of the bus line (i.e., in the SPI interface 11 in the example of FIG. 1) based on the transmitted data frames. This sender check sum is transmitted to the recipient (i.e., the bus master which is the MCU 12 in the present example of FIG. 1) on request and compared to a recipient check sum which is calculated by the recipient (the bus master) based on the received data frames. If the received data frames are equal to the transmitted data frames the CRC check sums calculated by sender and recipient are equal. If an error occurs during transmission at least one received data frame differs from the corresponding transmitted data frame and the respective CRC check sums (i.e., the recipient and the sender check sum) will differ. If a comparison of the recipient and the sender check sum yields that the check sums differ, the received data can be qualified as corrupt.

FIGS. 2 to 3 illustrate some exemplary implementations of the concept introduced above. FIG. 2 is a block diagram illustrating a first exemplary implementation of the novel concept. However, FIG. 2 does not include the complete airbag ECU 10 but only the components relevant for the further discussion. Accordingly, FIG. 2 includes, besides one external sensor 20, an SPI slave unit 11 (corresponding to the SPI interface 11 of FIG. 1) which provides the function of receiving data from the external sensor 20, converting it into data frames compliant with the bus protocol (i.e, the SPI standard in the examples herein), and transmitting it over the bus lines to an SPI master unit 120 which may be implemented in the MCU 12 (see FIG. 1). The SPI slave unit 11 may include a sensor interface 110 that is configured to receive measured data from external sensor(s) 20 and to convert the information obtained therefrom into data frames (data words of defined length, e.g., 32 bits). Each data frame may include a short check sum, for example a fourth order CRC check sum (CRC4). The data frames provided by the sensor interface 110 are handed on to the SPI interface 111 which is responsible for the bus communication in accordance with the bus protocol. In case of an SPI bus system four signals are involved in the bus communication. These signals are denoted as MISO (master input, slave output), MOSI (master output, slave input), SCLK (serial clock signal generated by the bus master), and SS (slave select signal). As the SPI bus system is sufficiently known in the art the details are not further discussed herein. In the present example, the SPI slave 11 sends data to the SPI master 120 using the bus line carrying the MISO signal.

A CRC unit 112 is coupled to the SPI interface 111. The CRC unit 112 receives (see arrow labeled “Data”) each data frame that is transmitted (or that is going to be transmitted) and configured to calculate an additional cumulative check sum as already explained above. An updated CRC check sum is calculated each time a data frame is transmitted, whereby the current check sum depends on all previous data frames transmitted after a reset (see arrow labeled “Reset”). In a similar way, the same CRC check sum may be calculated on the SPI master's end using a corresponding CRC unit 122 coupled to the bus master's SPI interface 121. The CRC unit 122 receives (see arrow labeled “Data”) each data frame that is received by the SPI interface 121. Further, the CRC unit 122 is also configured to calculate the additional cumulative check sum in the same way as the corresponding CRC unit 112 does on the bus slave's side. That is, an updated CRC check sum is calculated each time a data frame is received, whereby the current check sum depends on all previously received data frames starting from the latest reset (see arrow labeled “Reset”).

A CRC control unit 123 is coupled to the SPI master unit 120. As mentioned above, the CRC control unit 123 may be implemented in the MCU 12 using appropriate software. The CRC control unit 123 triggers the reset of the bus master's CRC unit 122 and the bus slave's CRC unit 112 (a respective reset command being sent over the bus lines in the latter case). The control unit 123 may further issue a fetch command over the bus so as to cause the bus slave's CRC unit 112 to send the current cumulative CRC check sum to the bus master 120 and eventually to the control unit 123 (see arrows labeled “fetch slave CRC” and “slave CRC from SPI”). The control unit 123 also has access to the CRC check sum (see arrows labeled “read” and “master CRC”) calculated on the bus master's side by CRC unit 122 and can therefore compare the check sums as already discussed above. If the check sums are identical the data is consistent; if not the data can be regarded as corrupt and, as a consequence, a safety function may be triggered. Such safety function may be, in the present example, the deactivation of the airbag firing interface 13 (see FIG. 1) thereby preventing an erroneous airbag deployment.

FIG. 3 is a block diagram illustrating an alternative to the implementation of FIG. 2. The example of FIG. 3 operates similarly to the previous example except that the master's and the slave's CRC check sum are compared at the slave's end of the SPI bus rather than at the master's end. In this case, the CRC control unit 123 is “distributed” across master and slave, i.e., a part 123′ of the control unit is implemented at the slave's end of the SPI bus. In the present example, the control unit 123 receives the CRC check sum calculated by the master CRC unit 122 and sends it to the CRC unit 112 on the slave's end via the SPI interface 111 (see arrow labeled “write master CRC”). The control unit 123′ (located at the slave's end of the bus) receives both CRC check sums from the slave CRC unit 112 as well as from the master CRC unit 122 (via the SPI bus lines) and compares the two check sums. In case that differences between the two corresponding check sums are detected, safety functions might by triggered directly by the control unit 123′ (via the security integrity check unit 141, see FIG. 1) or, alternatively an error message may be sent via the SPI bus to the CRC control unit 123 on the bus master's end. As mentioned above, one safety function may be to prevent an erroneous airbag deployment (either via the safety circuit 4 or by deactivation of the airbag firing interface 13). The CRC check sum calculated on the master's end may be pushed to the control unit 123′ at the slave's end at defined intervals (e.g., in response to the 20^(th) received data frame after a reset).

In the example of FIG. 4, the comparison of the CRC check sums provided by the SPI master 120 and the SPI slave 11 is provided by a separate SPI monitor unit 60 which may act as a second SPI slave and which may be included in the safety integrity check unit 141 (see FIG. 1). The SPI monitor 60 includes an SPI receiver interface 61 configured to receive messages over the bus from at least the bus master 120. As in the example of FIG. 2, the master requests the slave to send its current cumulative CRC check sum calculated on the bases of the data frames sent. The master sends both check sums to the SPI monitor 60 where the check sums are compared as mentioned above. The SPI interface 61 is typically configured to monitor all the data communication on the SPI bus and thus would receive all messages sent by the SPI slave 11 and SPI master 120. Dependent on the result of the comparison some error messages or security functions may be triggered. Such security function may be blocking an airbag deployment.

Although various exemplary embodiments of the invention have been disclosed, it will be apparent to those skilled in the art that various changes and modifications can be made which will achieve some of the advantages of the invention without departing from the spirit and scope of the invention. It will be obvious to those reasonably skilled in the art that other components performing the same functions may be suitably substituted. It should be mentioned that features explained with reference to a specific figure may be combined with features of other figures, even in those where not explicitly been mentioned. Further, the methods of the invention may be achieved in either all software implementations, using the appropriate processor instructions, or in hybrid implementations that utilize a combination of hardware logic and software logic to achieve the same results. Such modifications to the inventive concept are intended to be covered by the appended claims. 

1. A data transmission system comprising: at least one transmission line; a sender that is configured to send data frames to the at least one transmission line; a recipient that is configured to receive the data frames from the at least one transmission line, wherein the sender and the recipient are both configured to determine a check sum based on a plurality of corresponding data frames that are sent to and, respectively, received from the at least one transmission line; and a check sum comparing unit configured to receive and to compare the check sum determined by the sender and the corresponding check sum determined by the recipient, the check sum comparing unit being further configured to signal a transmission error or initiate a safety function when the check sums compared are not equal.
 2. The data transmission system of claim 1, wherein the sender and the recipient both comprise a check sum calculation unit that calculates a check sum based on the data frames which are sent to or, respectively, received from the at least one transmission line, wherein the calculated check sums are updated each time a data frame is sent or, respectively, received, and wherein the calculated check sums depend on all data frames that have been sent or, respectively, received after a reset of the check sum calculation units.
 3. The data transmission system of claim 1, wherein the check sum comparing unit is included in the sender, or in the recipient, or in a transmission line monitoring unit arranged separately from the sender and the recipient.
 4. The data transmission system of claim 1, wherein the check sum is a polynomial code check sum generated by a cyclic redundancy check (CRC).
 5. The data transmission system of claim 4, wherein each individual data frame includes a further check sum depending only on information included in the respective data frame.
 6. The data transmission system of claim 5, wherein the further check sum is a polynomial code check sum generated by a cyclic redundancy check, whereby the order of the further check sum is lower than the order of the check sums which are based on a plurality of corresponding data frames.
 7. The data transmission system of claim 3, wherein the check sum comparing unit is included in the sender and wherein the check sum determined by the recipient is sent to the check sum comparing unit via the at least one transmission line.
 8. The data transmission system of claim 3, wherein the check sum comparing unit is included in the recipient and wherein the check sum determined by the sender is sent to the check sum comparing unit via the at least one transmission line.
 9. The data transmission system of claim 3, wherein the check sum comparing unit is included in the transmission line monitoring unit and wherein the check sum determined by the sender and the check sum determined by the recipient are sent to the check sum comparing unit via the at least one transmission line.
 10. A bus system comprising: at least one bus line; a sender that is configured to send data frames to the at least one bus line; a recipient that is configured to receive the data frames from the at least one bus line, wherein the sender and the recipient are both configured to determine a check sum based on a plurality of corresponding data frames which are sent to and, respectively, received from the at least one bus line; and a check sum comparing unit configured to receive and to compare the check sum determined by the sender and the corresponding check sum determined by the recipient, the check sum comparing unit being further configured to signal a transmission error or to initiate a safety function when the check sums compared are not equal.
 11. The bus system of claim 10, wherein the bus system is compliant with the SPI bus standard.
 12. The bus system of claim 1, wherein the sender operates as bus slave and the recipient operates as bus master.
 13. The bus system of claim 10, wherein the sender and the recipient both comprise a check sum calculation unit that calculates a check sum based on the data frames that are sent to or, respectively, received from the at least one bus line; wherein the calculated check sums is updated each time a data frame is sent or, respectively, received; and wherein the calculated check sums depend on all data frames that have been sent or, respectively, received after a reset of the check sum calculation units.
 14. The bus system of claim 10, wherein the sender operates as bus slave and the recipient operates as bus master, and wherein the check sum comparing unit is included in the bus master, or in the bus slave, or in a bus monitoring unit arranged separately from the bus master and the bus slave.
 15. The bus system of claim 14, wherein the check sum comparing unit is included in the bus master and wherein the bus master requests the bus slave to send the current check sum via the at least one bus line.
 16. The bus system of claim 14, wherein the check sum comparing unit is included in the bus slave and wherein the bus master sends to the bus slave the current check sum via the at least one bus line.
 17. The bus system of claim 14, wherein the check sum comparing unit is included in the bus monitoring unit, wherein the bus master requests the bus slave to send the current check sum via the at least one bus line, and wherein the bus master sends to the bus monitoring unit both check sums via the at least one bus line.
 18. A method for transmitting data frames from a sender to a recipient over a transmission channel, the method comprising: receiving, from the sender's end, a check sum based on a plurality of data frames which are sent; receiving, from the recipient's end, a check sum based on a plurality of corresponding data frames which have been received; comparing the check sum received from the sender's end and the corresponding check sum received from the recipient's end; and signaling a transmission error when the check sums compared are not equal.
 19. The method of claim 18, further comprising resetting the check sum determination, wherein the received check sums depend on all data frames which have been sent or, respectively, received after a reset. 